feat: introduce Lakekeeper as REST catalog for Iceberg storage#4242
Draft
mengw15 wants to merge 42 commits intoapache:mainfrom
Draft
feat: introduce Lakekeeper as REST catalog for Iceberg storage#4242mengw15 wants to merge 42 commits intoapache:mainfrom
mengw15 wants to merge 42 commits intoapache:mainfrom
Conversation
github-actions
bot
added
engine
dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
This PR introduces Lakekeeper as a REST catalog service for Iceberg, replacing direct JDBC catalog connections. Key changes include:
bin/bootstrap-lakekeeper.sh): automates Lakekeeper setup with MinIO as the S3-compatible storage backend.bin/single-node/docker-compose.ymlto include Lakekeeper and MinIO services.Any related issues, documentation, discussions?
Closes #4126
How was this PR tested?
Tested manually on single-node Docker Compose deployment and Kubernetes cluster
Was this PR authored or co-authored using generative AI tooling?
co-authored with AI